Non-starting engine remote diagnostic

ABSTRACT

An engine diagnostic system includes an engine and a control system having a controller operatively connected to the engine. A monitoring system has a measurement device operatively connected to the engine. A diagnostic system is operatively connected to the engine. A communication system is configured to send and receive data from a remote location. The diagnostic system is configured to implement a non-starting engine diagnostic procedure, at least a portion of which is performed while the engine is cranking, and to transmit data generated during the engine diagnostic procedure to the remote location through the communication system.

RELATED APPLICATION(S)

This application is based on U.S. Provisional Application Ser. No.62/303,668, filed Mar. 4, 2016, the disclosure of which is incorporatedherein by reference in its entirety and to which priority is claimed.

FIELD

Various exemplary embodiments relate to performing remote enginediagnostic tests.

BACKGROUND

Modern engines are complex systems that can include numerous mechanicaland electrical components. Due to these complex systems, complexmonitoring and diagnostic testing are often required to detect anddiagnose failures or errors in the engine. Certain engines are equippedwith internal diagnostic systems. Internal systems however, may belimited in scope due to size, cost, or performance considerationsassociated with the engine. Technicians and service centers are oftenequipped with significantly more robust and sophisticated diagnosticcapabilities. The size and remote location use of some machines orvehicles can make it impractical to bring to a service center and thecomplexity of the systems can result in a technician that travels to thelocation of the machine having to spend a significant amount of timediagnosing the system and carry a large number of replacement parts tothe location.

Systems and methods of improving the diagnosis and service of the engine(and entire machines) can reduce the amount of time it takes atechnician to resolve an issue, and improve machine uptime and thecustomer experience. A common problem is that the engine will crank butnot start. Due to the complexity of modern engines and the large numberof potential causes that could prevent the engine from starting, atechnician must utilize sophisticated tools and follow multiple steps todiagnose the problem.

SUMMARY

According to an exemplary embodiment, an engine diagnostic systemincludes an engine and a control system having a controller operativelyconnected to the engine. A monitoring system has a measurement deviceoperatively connected to the engine. A diagnostic system is operativelyconnected to the engine. A communication system is configured to sendand receive data from a remote location. The diagnostic system isconfigured to implement a non-starting engine diagnostic procedure, atleast a portion of which is performed while the engine is cranking, andto transmit data generated during the engine diagnostic procedure to theremote location through the communication system.

Another exemplary embodiment is directed to a method of diagnosing anon-starting engine. A signal is sent to a diagnostic system operativelyconnected to an engine, the signal is sent through a communicationsystem configured to send and receive data from a remote location. Anon-starting engine diagnostic procedure is implemented in response tothe signal, wherein at least a portion of the non-starting enginediagnostic procedure is performed while the engine is cranking. Datagenerated during the non-starting engine diagnostic procedure related tothe non-starting engine is obtained and transmitted to the remotelocation through the communication system.

BRIEF DESCRIPTION OF THE DRAWINGS

The aspects and features of various exemplary embodiments will be moreapparent from the description of those exemplary embodiments taken withreference to the accompanying drawings, in which:

FIG. 1 is a schematic of an exemplary engine electronics system;

FIG. 2 is a flowchart illustrating an exemplary method of diagnosing anon-starting engine; and

FIG. 3 is a flowchart illustrating an exemplary diagnostic procedure fora non-starting engine.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

FIG. 1 shows an exemplary embodiment of an electronic processing system10 that is connected to an engine. The engine can be part of a vehiclethat contains one or more ground engaging members, for example tires ortreads, that are powered by the engine. Alternative embodiments can bedirected to other types of moving or stationary machines that utilize anengine, for example a diesel engine used in a generator.

In the exemplary embodiment shown in FIG. 1, the electronic processingsystem 10 includes a data bus 12 in communication with variouscomponents including a control system 14, a monitoring system 16, adiagnostic system 18, and a communication system 20. The electronicsystem 10 is configured to diagnose or at least partially diagnosedifferent error conditions in the engine, for example a non-startingcondition of the engine. Modern engines require sophisticated tools fordiagnostics and service. There are many steps a technician must followto diagnose an engine problem such as visual inspection, gathering data,or installing diagnostic tools. According to an exemplary embodiment,the diagnostic system 18 is connected to or integrated with theelectronic system 10 to perform interactive tests and calibrations, suchas a harness diagnostic test or injector calibration string input. Byretrieving information and performing interactive tests locally andtransmitting the data remotely, unnecessary diagnostic procedures can beeliminated or minimalized, allowing a technician to arrive at themachine with the right parts or a reduced range of parts.

The electronic processing system 10 can include one or more of a dataprocessor and data storage component. The electronic processing system10 can be implemented by a general purpose computer that is programmedwith software modules. The data bus 12 provides communication betweenthe different components. The control system 14 can include one or morecontrollers or electronic control units, for example an engine controlunit. The control system 14 can include software and/or firmware storedin memory to perform different operations and tasks.

The monitoring system 16 can include various sensors or othermeasurement devices used to monitor the status of components in theengine. For example, the monitoring system can collect voltageinformation associated with different sensors, and this information canbe compared to stored values in a chart or table. Based on discrepanciesbetween the actual and stored values, error codes or diagnostic troublecodes (DTCs) can be generated, either by the control system 14 or thediagnostic system 18.

The diagnostic system 18 can be configured to perform multiple tasks,including initiating tests and recording errors sensed by the monitoringsystem 16. For example, the diagnostic system 18 can receive and record,for example through a software module or instructions for analyzing, theresults of diagnostic tests, fault codes, error messages, statusmessages, or test results provided by the monitoring system 16. Thediagnostic system 18 can also be capable of analyzing or comparing theinformation provided by the monitoring system 16 to a database thatcontains prior information related to the engine and standard operatinginformation. The diagnostic system 18 can record and store dataassociated with the engine, and transfer that data via the communicationsystem 20 over a network to a remote location, for example a dealer orservice center.

The service center receives the transmitted data and then process thedata to provide a recommendation to a technician. The data can beprocessed by one or more data processing systems that can include aserver, central processing unit, software modules or programmable logic,and electronic memory. In certain instances, the recommendationidentifies a reduced number of potential sources of the problem from themaximum potential sources to allow the technician to carry fewer partsor equipment when visiting a location. The diagnostic system 18 also maybe capable of producing, storing, or communicating DTCs.

The communication system 20 is configured to locally and remotelycommunicate information over a communication network. The communicationsystem 20 can provide communication over different wired or wirelesssystems and networks including mobile, satellite, Wi-Fi, near-field,Bluetooth, or a combination thereof as needed. In an exemplaryembodiment, the communication system 20 is a telematics system. Thetelematics system includes, for example, a network of regional,national, or global hardware and software components. In addition, thetelematics service may be provided by a private enterprise, such as anindependent third-party company that provides the service to othercompanies, a manufacturing company that provides the service to itscustomers, or a company that provides the service to its own fleet ofvehicles. Alternatively, the telematics service may be provided by agovernmental agency as a public service. JDLink™ is an example of anagricultural vehicle telematics service, which is available from JohnDeere & Company.

The electronic processing system 10 can utilize other componentsincluding processors, data storage, data ports, user interface systems,controller area network buses, timers, etc., as would be understood byone of ordinary skill in the art.

According to an exemplary embodiment, the electronics system 10 isconfigured to perform a diagnostic based on a non-starting engine andtransfer generated information to a remote location. As shown in FIG. 2,a dealer or service center receives a complaint of a non-starting engine(100). The complaint can be from a customer call or generatedautomatically by the engine. An example of automatic generation caninclude the monitoring system 16 detecting multiple attempts to startthe engine in a certain time period without a successful engine startand/or detecting a prolonged time period of engine cranking. If thecomplaint is received automatically, the service center can contact auser to ensure that the user is with the machine and in a safe place toperform the additional steps.

The service center then informs the customer to keep the ignition on butthe engine off (102). A command is then sent remotely from the servicecenter to the machine (104), for example utilizing a remote servicetool, and a signal can be returned to indicate the request was received(106). The diagnostic system 18 then begins to record engine data andstart the test (108). The service center informs the customer to crankthe engine for a specified period of time, for example fifteen seconds,and then to leave the switch in the ‘on’ position (110). While theengine is cranking, one or more test are performed by the system 10, forexample the control system 14 and/or diagnostic system 18, andapplicable data is recorded (112). The tests can also place one or moreof the engine control units into a self-diagnostic mode (114). Once allthe tests are complete (116), the diagnostic system can stop recordingdata and retrieve one or more DTCs (118).

The test data and/or DTCs are then sent to the service center throughthe communication system 20 and analyzed by the service center (120).The gathered information is used to diagnose or narrow the problem forthe technician (122), who can load the necessary parts (124) and travelto the machine (126). Once at the machine, the technician can performfurther analyses and tests as needed (128). The technician can theninstall one or more replacement parts or perform a tasks to repair theengine (130) until the engine starts (132) and it is determined that themachine is operational (134).

FIG. 3 shows an exemplary embodiment of a test diagnostic procedure thatcan be run by the diagnostic system 18. After a signal is received tobegin the no-start diagnostic (200), a first check is performed todetermine if there are any presently generated DTCs (202). If there areany DTCs, they can be recorded and stored or sent to the service center.After the diagnostic system 18 checks for DTCs, any present DTCs can becleared.

The diagnostic system 18 then begins recording all parameters in ano-start engine category (204). In an exemplary embodiment the recordingis triggered by a detection of a minimum engine speed, for example 50revolutions per minute, with a 5 second pre-trigger continuous duration.This category will include different features and components based onthe type of engine and fuel system and can be, or be related to,components of the engine identified as commonly resulting in anon-starting condition. The system then determines if the engine isstopped (206), and waits for the engine to be started by a user. At thistime, the user begins to crank the engine for a time specified by theservice center.

While the engine is cranking, a timer starts and runs for apredetermined time period (208), for example a 60 second timer, althoughother time periods can be used. The procedure then monitors if theengine stops (210). If the engine is not stopped after the predeterminedtime period (212), an error can be issued and the test can be canceledor restarted (214). If the engine is stopped within the predeterminedtime period the diagnostic system 18 retrieves any DTCs that weregenerated (216). If there are any DTCs, they can be recorded and storedor sent to the service center. After the diagnostic system 18 checks forDTCs, any present DTCs can be cleared.

The diagnostic system 18 can then, if necessary, institute aself-diagnostic command to one or more controllers. For example aharness diagnostic mode test can be implemented (218). In an exemplaryembodiment, a harness diagnostic test includes a self-test that isprogrammed into the software of one or more controllers to assist indiagnosing electrical or mechanical engine problems that could cause ano-start situation. The functionality of the test varies depending onthe engine, fuel system, and features. Some of the actions that can beperformed include: Electrically energize the fuel injectors severaltimes while the ECU monitors the injector current waveform and detectfailures such as open or shorted circuits that result in a DTC; energizea high pressure fuel pump control solenoid(s) while the ECU monitors thecurrent and detect failures such as open or shorted circuits resultingin a DTC; energize the engine cold start aid (e.g., glow plugs) brieflyand verify that voltage is being applied to the device where a DTC wouldbe expected if a failure is detected; command a learn (zero and span) ofair system actuators (e.g., intake air throttle and exhaust gasrecirculation) where an actuator that is not responding correctly to thelearn command should result in a DTC; and test resistance of engineposition sensor circuits (e.g., camshaft and crankshaft position) wherea circuit that is out of range should result in a DTC. The harnessdiagnostic test can be run for a set period of time, for example 90seconds, and be monitored by a timer (220). The controller monitors theharness diagnostic test (222), and if the harness diagnostic is notcompleted within the predetermined time (224), an error can be generated(226).

After the harness diagnostic is completed, the diagnostic system canretrieve any generated DTCs (228) and stop recording data (230). TheDTCs and other recorded data are then sent to the service center foranalysis (232). The service center analyzes the data and makes arecommendation to a technician (234).

Accordingly, the above identified systems and procedures can be used toremotely diagnose or eliminate potential problems with a non-startingengine condition.

The foregoing detailed description of the certain exemplary embodimentshas been provided for the purpose of explaining the general principlesand practical application, thereby enabling others skilled in the art tounderstand the disclosure for various embodiments and with variousmodifications as are suited to the particular use contemplated. Thisdescription is not necessarily intended to be exhaustive or to limit thedisclosure to the exemplary embodiments disclosed. Any of theembodiments and/or elements disclosed herein may be combined with oneanother to form various additional embodiments not specificallydisclosed. Accordingly, additional embodiments are possible and areintended to be encompassed within this specification and the scope ofthe appended claims. The specification describes specific examples toaccomplish a more general goal that may be accomplished in another way.

As used in this application, the terms “front,” “rear,” “upper,”“lower,” “upwardly,” “downwardly,” and other orientational descriptorsare intended to facilitate the description of the exemplary embodimentsof the present disclosure, and are not intended to limit the structureof the exemplary embodiments of the present disclosure to any particularposition or orientation. Terms of degree, such as “substantially” or“approximately” are understood by those of ordinary skill to refer toreasonable ranges outside of the given value, for example, generaltolerances associated with manufacturing, assembly, and use of thedescribed embodiments.

What is claimed:
 1. An engine diagnostic system comprising: an engineand a control system having a controller operatively connected to theengine; a monitoring system having a measurement device operativelyconnected to the engine; a diagnostic system operatively connected tothe engine; and a communication system configured to send and receivedata from a remote location, wherein the diagnostic system is configuredto implement a non-starting engine diagnostic procedure, at least aportion of which is performed while the engine is cranking, and totransmit data generated during the engine diagnostic procedure to theremote location through the communication system.
 2. The enginediagnostic system of claim 1, wherein the diagnostic system isconfigured to implement a harness diagnostic test.
 3. The enginediagnostic system of claim 2, wherein the data includes diagnostictrouble codes.
 4. The engine diagnostic system of claim 1, wherein thenon-starting engine diagnostic procedure monitors and recordsinformation from engine components in a non-starting engine category. 5.The engine diagnostic system of claim 1, wherein the diagnostic systemis configured to record data after the engine begins cranking.
 6. Theengine diagnostic system of claim 1, wherein the remote locationincludes a communication module configured to send a signal to initiatethe non-starting engine diagnostic procedure.
 7. The engine diagnosticsystem of claim 1, wherein the engine is connected to a vehicle andoperatively connected to one or more ground engaging elements.
 8. Theengine diagnostic system of claim 1, wherein the communication system isconfigured to transmit data to a data processing system.
 9. The enginediagnostic system of claim 8, wherein the data processing system isconfigured to analyze the data and provide a recommendation based on theanalyzed data, and wherein the recommendation identifies a reducednumber of potential sources of a problem from a maximum amount ofpotential sources.
 10. The engine diagnostic system of claim 1, whereinthe communication system includes a telematics system.
 11. A method ofdiagnosing a non-starting engine comprising: sending a signal to adiagnostic system operatively connected to an engine, the signal sentthrough a communication system configured to send and receive data froma remote location; implementing a non-starting engine diagnosticprocedure in response to the signal, wherein at least a portion of thenon-starting engine diagnostic procedure is performed while the engineis cranking; obtaining data generated during the non-starting enginediagnostic procedure related to the non-starting engine; andtransmitting the data to the remote location through the communicationsystem.
 12. The method of claim 11, wherein the diagnostic system isconfigured to record one or more engine parameters during thenon-starting engine diagnostic procedure.
 13. The method of claim 11,further comprising a user cranking the engine during the non-startingengine diagnostic procedure for a set period of time.
 14. The method ofclaim 13, further comprising issuing an error if the engine is beingcranked after the set period of time.
 15. The method of claim 13,further comprising performing a harness diagnostic test during thenon-starting engine diagnostic procedure when the engine is not beingcranked.
 16. The method of claim 11, wherein the data includesdiagnostic trouble codes.
 17. The method of claim 11, further comprisingreceiving the data at the remote location and analyzing by a dataprocessing system.
 18. The method of claim 17, wherein the dataprocessing system is configured to analyze the data and provide arecommendation based on the analyzed data, and wherein therecommendation identifies a reduced number of potential sources of aproblem from a maximum amount of potential sources.
 19. The method ofclaim 18, further comprising presenting the recommendation to atechnician.
 20. The method of claim 11, wherein the signal is sent fromthe remote location.